Method, medium, and system for reducing product returns

ABSTRACT

A system and method of determining whether to make an item listing visible to a user are disclosed. A user is enabled to navigate an e-commerce site. A returns frequency index is calculated for the user based on the user&#39;s transaction history. The user&#39;s transaction history includes the user&#39;s history of item returns. It is determined whether or not to make an item listing visible to the user on the e-commerce site based on the returns frequency index for the user. In some embodiments, the returns frequency index is calculated using the mathematical expression (V Ret /N Ret )/(V Purch /N Purch ), wherein V Ret  is a total value of items returned by the user, N Ret  is a total number of items returned by the user, V Purch  is a total value of items purchased by the user, and N Purch  is a total number of items purchased by the user.

PRIORITY

This application is a continuation of and claims the benefit of priorityto U.S. patent application Ser. No. 13/658,592, filed on Oct. 23, 2012,which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present application relates generally to the technical field ofelectronic commerce (e-commerce), and, in various embodiments, tosystems and methods of determining whether to make an item listingvisible to a user based on the user's item return history.

BACKGROUND

One of the biggest concerns for e-commerce sellers is how to handlebuyers that frequently return items. When a buyer returns an item, theprocess can be quite involved. The seller typically has to arrange tohave the item returned, often in packaging, restock the returned item,and return the money to the buyer. These tasks consume valuable sellerresources. Additionally, when it comes to certain e-commerce sites, suchas eBay, the seller not only loses the sale revenue that has to bereturned to the buyer, but the seller is also typically responsible forthe cost of the return label that is used by the buyer to return theitem. Therefore, the seller has to pay for the buyer's decision toreturn the item.

A problem arises in how to expose e-commerce sellers to potential buyersthat are less likely to return items. There are a lot of people who arechronic returners. These chronic returners shop, try something theylike, and, even if they do not have any problem with the item, theystill return it because they have a habit of buying something and thenreturning it as soon as possible. This chronic returning creates aproblem for sellers, particularly small sellers that do not have theresources of big retailers.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments of the present invention are illustrated by way ofexample and not limitation in the figures of the accompanying drawings,in which like reference numbers indicate similar elements and in which:

FIG. 1 is a block diagram depicting a network architecture of a system,according to some embodiments, having a client-server architectureconfigured for exchanging data over a network;

FIG. 2 is a block diagram depicting a various components of anetwork-based publisher, according to some embodiments;

FIG. 3 is a block diagram depicting an example embodiment of varioustables that may be maintained within a database;

FIG. 4 is a block diagram illustrating an example embodiment of a systemthat determines whether to make an item listing visible to a user;

FIG. 5 is a flowchart illustrating an example embodiment of a method ofdetermining whether to make an item listing visible to a user; and

FIG. 6 shows a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions may beexecuted to cause the machine to perform any one or more of themethodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes illustrative systems, methods,techniques, instruction sequences, and computing machine programproducts that embody illustrative embodiments. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide an understanding of various embodiments ofthe inventive subject matter. It will be evident, however, to thoseskilled in the art that embodiments of the inventive subject matter maybe practiced without these specific details. In general, well-knowninstruction instances, protocols, structures, and techniques have notbeen shown in detail.

The present disclosure provides a way for sellers to protect themselvesfrom buyers that frequently return items. A returns frequency index canbe calculated for a buyer. This returns frequency index is an indicationof the risk that the buyer will return an item. This returns frequencyindex can be calculated using data from the buyer's transaction history,such as the total number of items returned by the buyer, the total valueof the items returned by the buyer, the total number of items purchasedby the buyer, and the total value of items purchased by the buyer. Aseller can restrict the visibility of his or her item listing to buyerswho have a certain returns frequency index, thereby preventing buyerswho do not meet the seller's standard for the returns frequency indexfrom viewing the seller's item listing. This visibility restrictionbased on the returns frequency index provides the seller with increasedprotection from the item being purchased by a buyer who is likely toreturn the item. This program of item listing visibility can be offeredto sellers as an option, and in some cases for a nominal fee.

In some embodiments, a user is enabled to navigate an e-commerce site. Areturns frequency index is generated for the user based on the user'stransaction history. The user's transaction history includes the user'shistory of item returns. It is determined whether or not to make an itemlisting visible to the user on the e-commerce site based on the returnsfrequency index for the user.

In some embodiments, the user's history of item returns includes a totalnumber of items the user has returned. In some embodiments, the user'shistory of item returns includes a total value of items the user hasreturned. In some embodiments, the user's transaction history furtherincludes a total number of items purchased by the user. In someembodiments, the user's transaction history further includes a totalvalue of items purchased by the user.

In some embodiments, generating the returns frequency index includesusing the mathematical expression(V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)), wherein V_(Ret) is a totalvalue of items returned by the user, N_(Ret), is a total number of itemsreturned by the user, V_(Purch) is a total value of items purchased bythe user, and N_(Purch) is a total number of items purchased by theuser. In some embodiments, an item listing is made invisible to the useron the e-commerce site in response to the returns frequency index forthe user being above a predetermined threshold.

In some embodiments, the user's transaction history upon which thereturns frequency index is based excludes returns caused by the user notreceiving an item within a predetermined amount of time and returnscaused by the user receiving an item different from what the userpurchased. In some embodiments, a seller of an item on the e-commercesite is enabled to select whether visibility of the item's listing tousers on the e-commerce site will be determined based on the returnsfrequency index for each user. In some embodiments, the visibility tothe user of the item listing on the e-commerce site is restricted basedon the returns frequency index for the user only after the user hasbuilt up a predetermined amount of transaction history on the e-commercesite.

FIG. 1 is a network diagram depicting a client-server system 100, withinwhich one example embodiment may be deployed. A networked system 102, inthe example forms of a network-based marketplace or publication system,provides server-side functionality, via a network 104 (e.g., theInternet or a Wide Area Network (WAN)) to one or more clients. FIG. 1illustrates, for example, a web client 106 (e.g., a browser, such as theInternet Explorer browser developed by Microsoft Corporation of Redmond,Wash. State) and a programmatic client 108 executing on respectiveclient machines 110 and 112.

An API server 114 and a web server 116 are coupled to, and provideprogrammatic and web interfaces respectively to, one or more applicationservers 118. The application servers 118 host one or more marketplaceapplications 120 and payment applications 122. The application servers118 are, in turn, shown to be coupled to one or more database servers124 that facilitate access to one or more databases 126.

The marketplace applications 120 may provide a number of marketplacefunctions and services to users who access the networked system 102. Thepayment applications 122 may likewise provide a number of paymentservices and functions to users. The payment applications 122 may allowusers to accumulate value (e.g., in a commercial currency, such as theU.S. dollar, or a proprietary currency, such as “points”) in accounts,and then later to redeem the accumulated value for products (e.g., goodsor services) that are made available via the marketplace applications120. While the marketplace and payment applications 120 and 122 areshown in FIG. 1 to both form part of the networked system 102, it willbe appreciated that, in alternative embodiments, the paymentapplications 122 may form part of a payment service that is separate anddistinct from the networked system 102.

Further, while the system 100 shown in FIG. 1 employs a client-serverarchitecture, the embodiments are, of course not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system, for example. The variousmarketplace and payment applications 120 and 122 could also beimplemented as standalone software programs, which do not necessarilyhave networking capabilities.

The web client 106 accesses the various marketplace and paymentapplications 120 and 122 via the web interface supported by the webserver 116. Similarly, the programmatic client 108 accesses the variousservices and functions provided by the marketplace and paymentapplications 120 and 122 via the programmatic interface provided by theAPI server 114. The programmatic client 108 may, for example, be aseller application (e.g., the TurboLister application developed by eBayInc., of San Jose, Calif.) to enable sellers to author and managelistings on the networked system 102 in an off-line manner, and toperform batch-mode communications between the programmatic client 108and the networked system 102.

FIG. 1 also illustrates a third party application 128, executing on athird party server machine 130, as having programmatic access to thenetworked system 102 via the programmatic interface provided by the APIserver 114. For example, the third party application 128 may, utilizinginformation retrieved from the networked system 102, support one or morefeatures or functions on a website hosted by the third party. The thirdparty website may, for example, provide one or more promotional,marketplace, or payment functions that are supported by the relevantapplications of the networked system 102.

FIG. 2 is a block diagram illustrating multiple applications 120 and 122that, in one example embodiment, are provided as part of the networkedsystem 102. The applications 120 and 122 may be hosted on dedicated orshared server machines (not shown) that are communicatively coupled toenable communications between server machines. The applications 120 and122 themselves are communicatively coupled (e.g., via appropriateinterfaces) to each other and to various data sources, so as to allowinformation to be passed between the applications 120 and 122 or so asto allow the applications 120 and 122 to share and access common data.The applications 120 and 122 may furthermore access one or moredatabases 126 via the database servers 124.

The networked system 102 may provide a number of publishing, listing,and price-setting mechanisms whereby a seller may list (or publishinformation concerning) goods or services for sale, a buyer can expressinterest in or indicate a desire to purchase such goods or services, anda price can be set for a transaction pertaining to the goods orservices. To this end, the marketplace applications 120 and 122 areshown to include at least one publication application 200 and one ormore auction applications 202, which support auction-format listing andprice setting mechanisms (e.g., English, Dutch, Vickrey, Chinese,Double, Reverse auctions etc.). The various auction applications 202 mayalso provide a number of features in support of such auction-formatlistings, such as a reserve price feature whereby a seller may specify areserve price in connection with a listing and a proxy-bidding featurewhereby a bidder may invoke automated proxy bidding.

A number of fixed-price applications 204 support fixed-price listingformats (e.g., the traditional classified advertisement-type listing ora catalogue listing) and buyout-type listings. Specifically, buyout-typelistings (e.g., including the Buy-It-Now (BIN) technology developed byeBay Inc., of San Jose, Calif.) may be offered in conjunction withauction-format listings, and allow a buyer to purchase goods orservices, which are also being offered for sale via an auction, for afixed-price that is typically higher than the starting price of theauction.

Store applications 206 allow a seller to group listings within a“virtual” store, which may be branded and otherwise personalized by andfor the seller. Such a virtual store may also offer promotions,incentives, and features that are specific and personalized to arelevant seller.

Reputation applications 208 allow users who transact, utilizing thenetworked system 102, to establish, build, and maintain reputations,which may be made available and published to potential trading partners.Consider that where, for example, the networked system 102 supportsperson-to-person trading, users may otherwise have no history or otherreference information whereby the trustworthiness and credibility ofpotential trading partners may be assessed. The reputation applications208 allow a user (for example, through feedback provided by othertransaction partners) to establish a reputation within the networkedsystem 102 over time. Other potential trading partners may thenreference such a reputation for the purposes of assessing credibilityand trustworthiness.

Personalization applications 210 allow users of the networked system 102to personalize various aspects of their interactions with the networkedsystem 102. For example a user may, utilizing an appropriatepersonalization application 210, create a personalized reference page atwhich information regarding transactions to which the user is (or hasbeen) a party may be viewed. Further, a personalization application 210may enable a user to personalize listings and other aspects of theirinteractions with the networked system 102 and other parties.

The networked system 102 may support a number of marketplaces that arecustomized, for example, for specific geographic regions. A version ofthe networked system 102 may be customized for the United Kingdom,whereas another version of the networked system 102 may be customizedfor the United States. Each of these versions may operate as anindependent marketplace or may be customized (or internationalized)presentations of a common underlying marketplace. The networked system102 may accordingly include a number of internationalizationapplications 212 that customize information (and/or the presentation ofinformation) by the networked system 102 according to predeterminedcriteria (e.g., geographic, demographic or marketplace criteria). Forexample, the internationalization applications 212 may be used tosupport the customization of information for a number of regionalwebsites that are operated by the networked system 102 and that areaccessible via respective web servers 116.

Navigation of the networked system 102 may be facilitated by one or morenavigation applications 214. For example, a search application (as anexample of a navigation application 214) may enable key word searches oflistings published via the networked system 102. A browse applicationmay allow users to browse various category, catalogue, or inventory datastructures according to which listings may be classified within thenetworked system 102. Various other navigation applications 214 may beprovided to supplement the search and browsing applications.

In order to make listings, available via the networked system 102, asvisually informing and attractive as possible, the applications 120 and122 may include one or more imaging applications 216, which users mayutilize to upload images for inclusion within listings. An imagingapplication 216 also operates to incorporate images within viewedlistings. The imaging applications 216 may also support one or morepromotional features, such as image galleries that are presented topotential buyers. For example, sellers may pay an additional fee to havean image included within a gallery of images for promoted items.

Listing creation applications 218 allow sellers to conveniently authorlistings pertaining to goods or services that they wish to transact viathe networked system 102, and listing management applications 220 allowsellers to manage such listings. Specifically, where a particular sellerhas authored and/or published a large number of listings, the managementof such listings may present a challenge. The listing managementapplications 220 provide a number of features (e.g., auto-relisting,inventory level monitors, etc.) to assist the seller in managing suchlistings. One or more post-listing management applications 222 alsoassist sellers with a number of activities that typically occurpost-listing. For example, upon completion of an auction facilitated byone or more auction applications 202, a seller may wish to leavefeedback regarding a particular buyer. To this end, a post-listingmanagement application 222 may provide an interface to one or morereputation applications 208, so as to allow the seller conveniently toprovide feedback regarding multiple buyers to the reputationapplications 208.

Dispute resolution applications 224 provide mechanisms whereby disputesarising between transacting parties may be resolved. For example, thedispute resolution applications 224 may provide guided procedureswhereby the parties are guided through a number of steps in an attemptto settle a dispute. In the event that the dispute cannot be settled viathe guided procedures, the dispute may be escalated to a third partymediator or arbitrator.

A number of fraud prevention applications 226 implement fraud detectionand prevention mechanisms to reduce the occurrence of fraud within thenetworked system 102.

Messaging applications 228 are responsible for the generation anddelivery of messages to users of the networked system 102, such as, forexample, messages advising users regarding the status of listings at thenetworked system 102 (e.g., providing “outbid” notices to bidders duringan auction process or to providing promotional and merchandisinginformation to users). Respective messaging applications 228 may utilizeany one of a number of message delivery networks and platforms todeliver messages to users. For example, messaging applications 228 maydeliver electronic mail (e-mail), instant message (IM), Short MessageService (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP))messages via the wired (e.g., the Internet), Plain Old Telephone Service(POTS), or wireless (e.g., mobile, cellular, WiFi, WiMAX) networks.

Merchandising applications 230 support various merchandising functionsthat are made available to sellers to enable sellers to increase salesvia the networked system 102. The merchandising applications 230 alsooperate the various merchandising features that may be invoked bysellers, and may monitor and track the success of merchandisingstrategies employed by sellers.

The networked system 102 itself, or one or more parties that transactvia the networked system 102, may operate loyalty programs that aresupported by one or more loyalty/promotions applications 232. Forexample, a buyer may earn loyalty or promotion points for eachtransaction established and/or concluded with a particular seller, andbe offered a reward for which accumulated loyalty points can beredeemed.

FIG. 3 is a high-level entity-relationship diagram, illustrating varioustables 300 that may be maintained within the database(s) 126, and thatare utilized by and support the applications 120 and 122. A user table302 contains a record for each registered user of the networked system102, and may include identifier, address and financial instrumentinformation pertaining to each such registered user. A user may operateas a seller, a buyer, or both, within the networked system 102. In oneexample embodiment, a buyer may be a user that has accumulated value(e.g., commercial or proprietary currency), and is accordingly able toexchange the accumulated value for items that are offered for sale bythe networked system 102.

The tables 300 also include an items table 304 in which are maintaineditem records for goods and services that are available to be, or havebeen, transacted via the networked system 102. Each item record withinthe items table 304 may furthermore be linked to one or more userrecords within the user table 302, so as to associate a seller and oneor more actual or potential buyers with each item record.

A transaction table 306 contains a record for each transaction (e.g., apurchase or sale transaction) pertaining to items for which recordsexist within the items table 304.

An order table 308 is populated with order records, each order recordbeing associated with an order. Each order, in turn, may be with respectto one or more transactions for which records exist within thetransaction table 306.

Bid records within a bids table 310 each relate to a bid received at thenetworked system 102 in connection with an auction-format listingsupported by an auction application 202. A feedback table 312 isutilized by one or more reputation applications 208, in one exampleembodiment, to construct and maintain reputation information concerningusers. A history table 314 maintains a history of transactions to whicha user has been a party. One or more attributes tables 316 recordattribute information pertaining to items for which records exist withinthe items table 304. Considering only a single example of such anattribute, the attributes tables 316 may indicate a currency attributeassociated with a particular item, the currency attribute identifyingthe currency of a price for the relevant item as specified by a seller.

FIG. 4 is a block diagram illustrating an example embodiment of a system400 that determines whether to make an item listing visible to a user.The system 400 comprises a navigation module 410 communicatively coupledto a returns frequency index module 420. The navigation module 410 isconfigured to enable a user 405 to navigate an e-commerce site. Thenavigation module 410 can incorporate the one or more navigationapplications 214, discussed above with respect to FIG. 2, in order toprovide searching and browsing functions, as well as other navigatingfunctions. In navigating the e-commerce site, the user 405 is able toview item listings. The navigation module 410 is configured to determinewhether or not to make an item listing visible to the user 405 based ona returns frequency index for the user 405.

The returns frequency index module 420 is communicatively coupled to thenavigation module 410 and is configured to generate a returns frequencyindex for the user 405. The returns frequency index indicates thelikelihood and risk that the buyer will return an item. The returnsfrequency index module 420 is configured to generate the returnsfrequency index based on the user's transaction history 435. Thetransaction histories 435 for the users 405 of the e-commerce site canbe stored in one or more databases 430. The user's transaction history435 includes the user's history of item returns. In some embodiments,the user's history of item returns includes a total number of items theuser 405 has returned. In some embodiments, the user's history of itemreturns includes a total value of items the user 405 has returned. Insome embodiments, the user's transaction history 435 includes a totalnumber of items purchased by the user 405. In some embodiments, theuser's transaction history 435 includes a total value of items purchasedby the user 405.

In some embodiments, the returns frequency index is generated using themathematical expression (V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)), whereinV_(Ret) is a total value of items returned by the user, N_(Ret) is atotal number of items returned by the user, V_(Purch) is a total valueof items purchased by the user, and N_(Purch) is a total number of itemspurchased by the user. In some embodiments, the returns frequency indexcan equal (V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)). In other embodiments,the returns frequency index can be generated using(V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)) within a larger mathematicalexpression. In some embodiments, an item listing is made invisible tothe user 405 on the e-commerce site in response to the returns frequencyindex for the user 405 being above a predetermined threshold. Forexample, in some embodiments, an item listing is made invisible to theuser 405 if the returns frequency index for the user 405 is greater than0.25.

In some embodiments, visibility of item listings to the user 405 is notlimited until the user 405 builds up a predetermined amount oftransaction history, thereby providing a grace period for new users 405.Without this grace period, if a new user 405 buys and returns his firstitem, then he could be penalized right away, having his visibility ofcertain item listings restricted going forward. Such a scenario could beundesirable for sellers, as new users 405 could be excluded from viewingtheir item listings even though there is not yet enough information toindicate that these new users 405 are a high risk for returning items.In some embodiments, the grace period for item listings on an e-commercesite can be configured by a site administrator. In some embodiments, aseller can configure the grace period for his or her own listing.

In some embodiments, the returns frequency index module 420 may beconfigured to generate the returns frequency index based on a particularrestricted use of the user's transaction history 435. For example, insome embodiments, the returns frequency index module 420 may beconfigured to generate a returns frequency index based on a usertransaction history 435 that does not include returns caused by the user405 not receiving an item in a timely manner. Additionally, in someembodiments, the returns frequency index module 420 may be configured togenerate a returns frequency index based on a user transaction history435 that does not include returns caused by the user 405 receiving anitem different from what the user 405 purchased (e.g., purchasing aniPhone and receiving an iPod). In some embodiments, a site administratormay identify and configure what portions of the transaction history 435are used in calculating the returns frequency index. In someembodiments, a seller may identify and configure what portions of thetransaction history 435 are used in calculating the returns frequencyindex for determining visibility for his or her own listing.

FIG. 5 is a flowchart illustrating an example embodiment of a method 500of determining whether to make an item listing visible to a user.

At operation 510, the seller of an item configures the visibility of hisor her item listing on an e-commerce site. The e-commerce site's systemmay receive, from the seller, configuration information that configuresthe visibility of the seller's item listing on the e-commerce site andmay store it in a database. It is contemplated that the visibility canadditionally or alternatively be configured by a site administrator sothat the particular visibility configuration applies to multiple itemlistings belonging to different sellers. This visibility configurationcan include, but is not limited to, the returns frequency indexvisibility threshold, how to calculate the returns frequency index, andthe grace period discussed above.

At operation 520, the e-commerce site's system stores user transactionhistories for users of its site. As previously discussed, each usertransaction history can include a user's history of item returns. Insome embodiments, the user's history of item returns includes a totalnumber of items the user has returned. In some embodiments, the user'shistory of item returns includes a total value of items the user hasreturned. In some embodiments, the user's transaction history includes atotal number of items purchased by the user. In some embodiments, theuser's transaction history includes a total value of items purchased bythe user.

At operation 530, a user may perform a navigating action on thee-commerce site that would ordinarily lead to a viewing of the seller'sitem listing, which has been configured with a particular visibilitysetting. Such navigating action can include, but is not limited to,searching and browsing.

At operation 540, the e-commerce site's system determines whether or notthe user has the minimum amount of transaction history needed to use thereturns frequency index. If the user does not have the minimum amount oftransaction historyneeded, such as if the user is brand new to using thee-commerce site, then the user is within the grace period and thee-commerce site makes the seller's item listing visible to the user atoperation 570A. If the user does have the minimum amount of transactionhistoryneeded, then the system proceeds to use the returns frequencyindex as a standard for visibility of the item listing to the user.

At operation 550, the system generates the returns frequency index forthe user based on the user's transaction history. It is contemplatedthat the returns frequency index for the user may have been previouslygenerated and stored by the system prior to the user performing thenavigating action at operation 530. As previously discussed, the user'stransaction history may include the history of item returns for theuser. In some embodiments, the history of item returns for the userincludes a total number of items the user 405 has returned. In someembodiments, the history of item returns for the user includes a totalvalue of items the user 405 has returned. In some embodiments, theuser's transaction history includes a total number of items purchased bythe user 405. In some embodiments, the user's transaction historyincludes a total value of items purchased by the user 405. In someembodiments, the returns frequency index is generated using themathematical expression (V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)), whereinV_(Ret) is a total value of items returned by the user, N_(Ret) is atotal number of items returned by the user, V_(Purch) is a total valueof items purchased by the user, and N_(Purch) is a total number of itemspurchased by the user. In some embodiments, the returns frequency indexcan equal (V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)). In other embodiments,the returns frequency index can be generated using(V_(Ret)/N_(Ret))/(V_(Purch)/N_(Purch)) within a larger mathematicalexpression.

At operation 560, the system may determine whether or not the itemlisting is made visible to the user by comparing the returns frequencyindex for the user with a visibility standard configured by the selleror administrator at operation 510. For example, if the returns frequencyindex for the user does meet the standard, then the item listing is madevisible to the user at operation 570A. Contrawise, if the returnsfrequency index for the user does not meet the standard, then the itemlisting is made invisible to the user at operation 570B.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client, or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the network 104 of FIG. 1) and via one or moreappropriate interfaces (e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor,a computer, or multiple computers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry(e.g., a FPGA or an ASIC).

A computing system can include clients and servers. A client and serverare generally remote from each other and typically interact through acommunication network. The relationship of client and server arises byvirtue of computer programs running on the respective computers andhaving a client-server relationship to each other. In embodimentsdeploying a programmable computing system, it will be appreciated thatboth hardware and software architectures merit consideration.Specifically, it will be appreciated that the choice of whether toimplement certain functionality in permanently configured hardware(e.g., an ASIC), in temporarily configured hardware (e.g., a combinationof software and a programmable processor), or a combination ofpermanently and temporarily configured hardware may be a design choice.Below are set out hardware (e.g., machine) and software architecturesthat may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 6 is a block diagram of a machine in the example form of a computersystem 600 within which instructions for causing the machine to performany one or more of the methodologies discussed herein may be executed.In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 600 includes a processor 602 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 604 and a static memory 606, which communicate witheach other via a bus 608. The computer system 600 may further include avideo display unit 610 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 600 also includes analphanumeric input device 612 (e.g., a keyboard), a user interface (UI)navigation (or cursor control) device 614 (e.g., a mouse), a disk driveunit 616, a signal generation device 618 (e.g., a speaker) and a networkinterface device 620.

Machine-Readable Medium

The disk drive unit 616 includes a machine-readable medium 622 on whichis stored one or more sets of data structures and instructions 624(e.g., software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 624 mayalso reside, completely or at least partially, within the main memory604 and/or within the processor 602 during execution thereof by thecomputer system 600, the main memory 604 and the processor 602 alsoconstituting machine-readable media. The instructions 624 may alsoreside, completely or at least partially, within the static memory 606.

While the machine-readable medium 622 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions 624 or data structures. The term “machine-readablemedium” shall also be taken to include any tangible medium that iscapable of storing, encoding or carrying instructions for execution bythe machine and that cause the machine to perform any one or more of themethodologies of the present embodiments, or that is capable of storing,encoding or carrying data structures utilized by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including by way of example semiconductormemory devices (e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM), and flashmemory devices); magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and compact disc-read-onlymemory (CD-ROM) and digital versatile disc (or digital video disc)read-only memory (DVD-ROM) disks.

Transmission Medium

The instructions 624 may further be transmitted or received over acommunications network 626 using a transmission medium. The instructions624 may be transmitted using the network interface device 620 and anyone of a number of well-known transfer protocols (e.g., HTTP). Examplesof communication networks include a LAN, a WAN, the Internet, mobiletelephone networks, POTS networks, and wireless data networks (e.g.,WiFi and WiMax networks). The term “transmission medium” shall be takento include any intangible medium capable of storing, encoding, orcarrying instructions for execution by the machine, and includes digitalor analog communications signals or other intangible media to facilitatecommunication of such software.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the present disclosure. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense. The accompanying drawings that form a parthereof, show by way of illustration, and not of limitation, specificembodiments in which the subject matter may be practiced. Theembodiments illustrated are described in sufficient detail to enablethose skilled in the art to practice the teachings disclosed herein.Other embodiments may be utilized and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. This Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

What is claimed is:
 1. A system comprising: at least one processor; areturns frequency index module, executable by the at least oneprocessor, configured to generate a returns frequency index for a userbased on the a transaction history for the user, the transaction historyfor the user includes a history of item returns for the user; and anavigation module, executable by the at least one processor, configuredto: enable the user to navigate an e-commerce site, and determinewhether to make an item listing visible to the user on the e-commercesite based on the returns frequency index for the user.